Mapping and bridging wireless networks to provide better service

ABSTRACT

Methods, systems, computer-readable media, and apparatuses for providing service to access nodes are presented. In some embodiments, a computing device may generate a geographical coverage map comprising a plurality of wireless access nodes respectively at a plurality of geographic locations and a wireless coverage range for each wireless access node. The computing device may receive from at least one wireless access node of the plurality of wireless access nodes an indication that the at least one wireless access node detected a first wireless access node of the plurality of wireless access nodes. The computing device may refine a first coverage range of the first wireless access node based on a respective geographic location of the at least one wireless access node. In some embodiments, a first wireless access node may receive and forward join emergency mesh (JEM) messages to establish a wireless network.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is related to U.S. application Ser. No. 14/259,040filed on Apr. 22, 2014, entitled “Determining Wireless CoverageInformation Using Wireless Access Points,” the disclosure of which ishereby incorporated by reference in its entirety.

FIELD OF ART

Aspects of the disclosure present methods and systems relate to coveragearea information of access nodes and using such information, forexample, to establish a wireless network connecting the access nodes toimprove service, for example, during emergencies or disasters.

BACKGROUND

Service providers have deployed a large number of wireless-enableddevices (e.g., modems, routers, etc.) to users (e.g., subscribers,customers, etc.). However, service providers have little knowledgeregarding the actual wireless service area covered by these devices andalso have little ability to detect unauthorized devices that arespoofing a user's authorized device, for example, at locations outsideof the customer's residence or business. Additionally, service providersgenerally provide service to the wireless-enabled devices throughinterconnected communication lines (e.g., coaxial cables, opticalfibers, etc.). Because these lines have a fixed maximum bandwidth, thereis an inherent fixed amount of data that a user's device can receivethough those lines at any given time. Further, the service provider maynot be able to provide any bandwidth to some of the devices in the eventof a network outage caused by, for example, a disaster or accidentresulting in a cut in the communication lines and/or disablement of aservice-providing headend device. In such instances, the serviceprovider may not be able to broadcast a message to the devices.

SUMMARY

The following presents a simplified summary in order to provide a basicunderstanding of some aspects of the disclosure. This summary is not anextensive overview of the disclosure. It is not intended to identify keyor critical elements of the disclosure or to delineate the scope of thedisclosure. The following summary merely presents some concepts of thedisclosure in a simplified form as a prelude to the more detaileddescription provided below.

In some embodiments, a computing device may generate a geographicalcoverage map comprising a plurality of wireless access nodesrespectively at a plurality of geographic locations and a wirelesscoverage range for each wireless access node. The computing device mayreceive from at least one wireless access node of the plurality ofwireless access nodes an indication that the at least one wirelessaccess node detected a first wireless access node of the plurality ofwireless access nodes. The computing device may refine a first coveragerange of the first wireless access node based on a respective geographiclocation of the at least one wireless access node.

In some embodiments, a first wireless access node may receive, from asecond wireless access node within a wireless range of the firstwireless access node, a join emergency mesh (JEM) message comprising arequest to establish a wireless network at least between the firstwireless access node and the second wireless access node. The JEMmessage may indicate that the second wireless access node does not havenetwork connectivity to a headend device. The first wireless access nodemay detect that the first wireless access node does not have networkconnectivity to the headend device. The first wireless access node mayforward the JEM message to a third wireless access node different fromthe second wireless access node. The third wireless access node may bewithin the wireless range of the first wireless access node.

In some embodiments, a first wireless access node may receive a joinemergency mesh (JEM) message and a first private service set identifier(SSID) from a second wireless access node using a public SSID. Inresponse to a determination that the first wireless access node does nothave network connectivity with a headend device, the first wirelessaccess node may send the JEM message and a second private SSID of thefirst wireless access node to a third wireless access node using thepublic SSID. The third wireless access node may be different from thesecond wireless access nodes. The first wireless access node mayestablish a wireless network between the first wireless access node andthe second wireless access node using the first private SSID and thefirst wireless access node and the third wireless access node using thesecond private SSID.

Aspects of the disclosure may be provided in a system, an apparatus, ora computer-readable medium having computer-executable instructions toperform one or more of the process steps described herein.

These features, along with many others, are discussed in greater detailbelow.

BRIEF DESCRIPTION OF THE DRAWINGS

A more complete understanding of the present disclosure and theadvantages thereof may be acquired by referring to the followingdescription in consideration of the accompanying drawings, in which likereference numbers indicate like features, and wherein:

FIG. 1 illustrates an exemplary network in accordance with variousaspects of the disclosure.

FIG. 2 illustrates an exemplary hardware and software platform on whichvarious elements described herein can be implemented in accordance withvarious aspects of the disclosure.

FIG. 3 illustrates an exemplary wireless coverage map of multiplewireless access points in an area in accordance with one or moreillustrative aspects discussed herein.

FIG. 4 illustrates a flowchart of an exemplary method for detectingtheft of service in accordance with one or more illustrative aspectsdiscussed herein.

FIG. 5 illustrates an exemplary system for establishing a wirelessnetwork in accordance with one or more illustrative aspects discussedherein.

FIG. 6 illustrates a flowchart of an exemplary method for establishing awireless network in accordance with one or more illustrative aspectsdiscussed herein.

FIG. 7 illustrates an exemplary system for optimizing a wireless networkin accordance with one or more illustrative aspects discussed herein.

FIG. 8 illustrates a flowchart of an exemplary method for optimizing awireless network in accordance with one or more illustrative aspectsdiscussed herein.

FIG. 9 illustrates an exemplary system for modeling a wireless networkin accordance with one or more illustrative aspects discussed herein.

FIG. 10 illustrates a flowchart of an exemplary method for modeling awireless network in accordance with one or more illustrative aspectsdiscussed herein.

DETAILED DESCRIPTION

In the following description of various illustrative embodiments,reference is made to the accompanying drawings identified above, whichform a part hereof, and in which is shown by way of illustration variousembodiments in which aspects of the disclosure may be practiced. Otherembodiments may be utilized and structural and functional modificationsmay be made, without departing from the scope discussed herein. Variousaspects are capable of other embodiments and of being practiced or beingcarried out in various different ways. In addition, the phraseology andterminology used herein are for the purpose of description and shouldnot be regarded as limiting. Rather, the phrases and terms used hereinare to be given their broadest interpretation and meaning. The use of“including” and “comprising” and variations thereof is meant toencompass the items listed thereafter and equivalents thereof as well asadditional items and equivalents thereof.

FIG. 1 illustrates an example network 100, such as a telecommunicationsor a content delivery network, on which many of the various featuresdescribed herein may be implemented. The network 100 may be any type ofinformation distribution network, such as satellite, telephone,cellular, wireless, etc. One example may be an optical fiber network, acoaxial cable network, or a hybrid fiber/coax (HFC) distributionnetwork. Such networks 100 may use a series of interconnectedcommunication lines 101 a (e.g., coaxial cables, optical fibers,wireless links, etc.) to connect access nodes 140 and other locations102 (e.g., businesses, homes, consumer dwellings, etc.) to a centrallocation or office (e.g., headend) 103. The central office 103 maytransmit downstream information signals onto the lines 101 a to theaccess nodes 140 and other locations 102. Each access node 140 and otherlocations 102 may have a receiver used to receive and process thosesignals.

There may be one line 101 a originating from the central office 103, andit may be split a number of times to distribute the signal to variousaccess nodes 140 and other locations 102 in the vicinity (which may bemany miles) of the central office 103. Herein, the access nodes 140 mayrefer to hardware modules including e.g., a device 130, such as a modem,and a gateway interface 131. In some aspects, an access node 140 mayrefer to a wireless (e.g., Wi-Fi, etc.) hotspot that allows various userdevices 116 (wireless laptops and netbooks, mobile phones, mobiletelevisions, personal digital assistants (PDA), etc.) to connect tonetwork 100 and external networks 109 for access to various content,including content found over the Internet. Device 130 may includetransmitters and receivers used to communicate on the lines 101 a andwith the central office 103. Within a given access node 140, the device130 may be, for example, a coaxial cable modem (for the coaxial cablelines 101 a), a fiber interface node (for the fiber optic lines 101 a),or any other desired device. Meanwhile, the gateway interface device 131may be a computing device (e.g., a router for wireless (e.g., Wi-Fi,etc.) connectivity, etc.) that communicates with the device 130 to allowone or more wireless devices 116 to communicate with the central office103 and other devices beyond the central office 103, such as thosedevices connected to the external networks 109. The gateway 131 may alsoinclude wireless network interfaces (not shown) to provide communicationsignals to wireless devices 116. The access node 140 may transmit morethan one wireless network identifier (e.g., SSID). For example, theaccess node 140 may transmit one network identifier which isconfigurable by a subscriber or user and another network identifierwhich is only configurable by the service provider.

Meanwhile, the locations 102 may be any type of user premises, such ashomes, businesses, institutions, etc. The lines 101 a may includecomponents not illustrated, such as splitters, filters, amplifiers, etc.to help convey the signal clearly, but in general each split introducesa bit of signal degradation. Portions of the lines 101 a may also beimplemented with fiber-optics, while other portions may be implementedwith other types of lines or wireless communication paths.

The central office 103 may include an interface, such as a terminationsystem (TS) 104. More specifically, the interface 104 may be a cablemodem termination system (CMTS), which may be a computing deviceconfigured to manage communications between devices on the network oflines 101 a and backend devices such as servers 105-108 (to be discussedfurther below). Backend devices such as servers 105-108 may be locatedin close proximity to one another (e.g., in the same building) and/orfar apart (e.g., separate cities, countries, etc.) and may be connectedto one another over various communication platforms, including over acloud computing environment. The interface 104 may be as specified in astandard, such as, in an example of an HFC-type network, the Data OverCable Service Interface Specification (DOCSIS) standard, published byCable Television Laboratories, Inc. (a.k.a. CableLabs), or it may be asimilar or modified device instead. The interface 104 may be configuredto place data on one or more downstream channels or frequencies to bereceived by devices, such as modems 130, 110 at the various access nodes140 and other locations 102, and to receive upstream communications fromthe devices 130, 110 on one or more upstream channels or frequencies.

The central office 103 may also include one or more network interfaces170, which can permit the central office 103 to communicate with variousother external networks 109. That is, the network interface 170 mayinclude circuitry needed to communicate with one or more externalnetworks 109 and their corresponding devices. These external networks109 may include, for example, networks of Internet devices, telephonenetworks, cellular telephone networks, fiber optic networks, localwireless networks (e.g., WiMAX), satellite networks, and any otherdesired network. For example, the external network 109 may include acellular telephone network 109 a and its corresponding cell phones 109b.

As noted above, the central office 103 may include a variety of servers105-108 that may be configured to perform various functions, includingproviding content to access nodes 140 and other locations 102, the cellphones 109 b, and other devices on the external networks 109. Forexample, the central office 103 may include a push notification server105. The push notification server 105 may generate push notifications todeliver data and/or commands to various access nodes 140 and otherlocations 102 in the network (or more specifically, to the devices inaccess nodes 140 and other locations 102 that are configured to detectsuch notifications). The central office 103 may also include a contentserver 106. The content server 106 may be one or more computing devicesthat are configured to provide content to users at the access nodes 140and/or the locations 102. This content may be, for example, video ondemand movies, television programs, songs, text listings, etc. Thecontent server 106 may include software to validate user identities andentitlements, locate and retrieve requested content, encrypt thecontent, and initiate delivery (e.g., streaming) of the content to therequesting user and/or device.

The central office 103 may also include one or more application servers107. An application server 107 may be a computing device configured tooffer any desired service, and may run various languages and operatingsystems (e.g., servlets and JSP pages running on Tomcat/MySQL, OSX, BSD,Ubuntu, Redhat, HTML5, JavaScript, AJAX and COMET). For example, anapplication server 107 may be responsible for collecting data such astelevision program listings information and generating a data downloadfor electronic program guide listings. Another application server 107may be responsible for monitoring user viewing habits and collectingthat information for use in selecting advertisements. Anotherapplication server 107 may be responsible for formatting and insertingadvertisements in a video stream being transmitted to the access nodes140 and other locations 102. And another application server 107 may beresponsible for receiving user remote control commands, and processingthem to provide an intelligent remote control experience.

An example location 102 a (e.g., one of locations 102) may include aninterface 120. The interface 120 can include any communication circuitryneeded to allow a device to communicate on one or more links 101 withother devices in the network. Similar to an access node 140, theinterface 120 may comprise a device 110, such as a modem, which may alsoinclude transmitters and receivers used to communicate on the lines 101a and with the central office 103. The device 110 may be, for example,an embedded digital voice adapter (eDVA), an embedded multimedia adapter(eMTA), a coaxial cable modem (for coaxial cable lines 101), a fiberinterface node (for the fiber optic lines 101), twisted-pair telephonemodem, cellular telephone transceiver, satellite transceiver, localwi-fi router or access point, or any other desired modem device. Also,although only one modem is shown in FIG. 1, a plurality of modemsoperating in parallel may be implemented within the interface 120. Thedevice 110 may be connected to, or be a part of, a gateway interfacedevice 111. Similar to the gateway interface device 131, the gatewayinterface device 111 may be a computing device that communicates withthe device 110 to allow one or more other devices at the location 102 ato communicate with the central office 103 and other devices beyond thecentral office 103, such as those devices connected to the externalnetworks 109. In some embodiments, the gateway interface device 111 mayoperate to communicate with devices 112-116 located over a smallerdistance than the distance between gateway 131 and user devices 116. Thegateway 111 may be a set-top box (STB), a digital transport adapter(DTA), a digital video recorder (DVR), computer server, or any otherdesired computing device. The gateway 111 may also include local networkinterfaces (not shown) to provide communication signals to devices112-116 at the location 102 a, such as display devices 112 (e.g.,televisions), additional STBs or DVRs 113, personal computers 114,laptop computers 115, wireless devices 116 (e.g., wireless routers,wireless laptops and netbooks, notebooks, tablets, cordless phones,mobile phones, mobile televisions, personal digital assistants (PDAs),etc.), landline phones 117 (e.g. Voice over Internet Protocol—VoIPphones), and any other desired devices. Examples of the local networkinterfaces include Multimedia Over Coax Alliance (MoCA) interfaces,Ethernet interfaces, universal serial bus (USB) interfaces, wirelessinterfaces (e.g., IEEE 802.11), Bluetooth interfaces, and others.

In addition to the examples of the term “access node” provided above,the term “access node” 140, “wireless access node,” “access point” or“wireless access point” as used herein may also refer to one or moredevices at the locations 102 including, for example, the interface 120,the device 110 (e.g., a cable modem such as an eMTA and/or a wirelessrouter to provide a Wi-Fi hotspot), the devices 116, or any othercomputing device discussed in connection with sample location 102 a.

In addition, the central office 103 may include a node location server108 to receive data (e.g., wireless coverage data) collected by variousdeployed access nodes. The server 108 may analyze the collected data togenerate estimate locations of access points unknown to the server 108and to estimate coverage data (e.g., maps) of the area. In performingthese functions, server 108 may also request, collect, store, andanalyze various data from the access nodes 140 including systeminformation (e.g., maps), and/or wireless (e.g., Wi-Fi) received signalstrength indicator (RSSI) levels, SSID, communication channelinformation, and device identifier information of access pointsoperating in the area.

The node location server 108 may also be referred to herein as a “meshserver.” The mesh server 108 may model potential wireless mesh networksand may create one or more wireless mesh networks (e.g., an ad hoc Wi-Finetwork) by sending instructions and/or configuration files to theaccess nodes 140 to form the one or more wireless mesh networks. Awireless mesh network may include one or more access nodes 140. Thewireless mesh network may be formed by bridging the wireless connectionsof neighboring access nodes 140 with one another to enable communicationbetween the access nodes 140. Each wireless mesh network may include oneor more egress access nodes (e.g., the access nodes 140 that haveconnectivity over a distribution network to the central office 103). Thedistribution network may include one or more devices of the centraloffice 103 (e.g., a CMTS) and/or one or more links 101 (e.g., lines 101a, etc.) connected to that particular access node 140 from which theaccess node 140 typically receives service from the central office 103.

Once a wireless mesh network is established among multiple access nodes140, the mesh server 108 may configure the access nodes 140 to perform anumber of functions. In one example, the access nodes 140 may detect andreport the detection of devices and/or other access nodes 140 to themesh server 108. The mesh server 108 may determine if there has been atheft of service based on, for example, a comparison of where an accessnode 140 is determined to be approximately located and the location ofthe access node 140 stored in a database of the central office 103. Inanother example, the mesh server 108 may provision and/or enable one ormore particular access nodes 140 to receive a bandwidth and a data speedgreater than that of the maximum bandwidth capacity and data speed ofparticular lines 101 a connected to those particular access nodes 140.For example, the particular access points 140 may, using the wirelessmesh network, connect to one or more other access nodes 140 that areconnected to one or more different lines 101 a to receive the additionalbandwidth and/or throughput. In another example, the mesh server 108 maytransmit messages to each access node 140 through one or more wirelessmesh networks. Each access node 140 may, upon receiving the message,output the message to its user (e.g., subscriber, customer, etc.) andmay forward (e.g., relay or propagate) the message to other access nodes140. In yet another example, the mesh server 108 may configure theaccess nodes 140 to establish the one or more wireless mesh networks inresponse to an emergency or disaster affecting one or more distributionnetworks. For example, the mesh server 108 and/or the access nodes 140may begin establishing the wireless mesh network in response todetermining a loss of network connectivity over one of the distributionnetworks for a predetermined time period.

Although shown separately, one of ordinary skill in the art willappreciate that the push server 105, the content server 106, theapplication server 107, and the mesh server 108 may be combined.Further, here the push server 105, the content server 106, theapplication server 107, and the mesh server 108 are shown generally, andit will be understood that they may each contain memory storing computerexecutable instructions to cause a processor to perform steps describedherein and/or memory for storing data.

FIG. 2 illustrates general hardware elements that can be used toimplement any of the various computing devices discussed herein. Thecomputing device 200 may include one or more processors 201, which mayexecute instructions of a computer program to perform any of thefeatures described herein. The instructions may be stored in any type ofcomputer-readable medium or memory, to configure the operation of theprocessor 201. For example, instructions may be stored in a read-onlymemory (ROM) 202, a random access memory (RAM) 203, removable media 204,such as a Universal Serial Bus (USB) drive, compact disk (CD) or digitalversatile disk (DVD) drive, and/or floppy disk drive, or any otherdesired electronic storage medium. Instructions and/or other data mayalso be stored in an attached (or internal) hard drive and/or datarepository 205. The computing device 200 may include one or more outputdevices, such as a display 206 (e.g., an external television), and mayinclude one or more output device controllers 207, such as a videoprocessor. There may also be one or more user input devices 208, such asa remote control, keyboard, mouse, touch screen, microphone, etc. Thecomputing device 200 may also include one or more network interfaces,such as input/output circuits 209 (e.g., a network card) to communicatewith a network 210. The network interface 209 may be a wired interface,wireless interface, or a combination of the two. In some embodiments,the network interface 209 may include a device (e.g., a cable modem),and the network 210 may include the communication lines 101 a discussedabove, the external network 109, an in-home network, a provider'swireless, coaxial, fiber, or hybrid fiber/coaxial distribution system(e.g., a DOCSIS network), or any other desired network. Additionally,the device may include a location-detecting device, such as a globalpositioning system (GPS) microprocessor 211, which can be configured toreceive and process global positioning signals and determine, withpossible assistance from an external server and antenna, a geographicposition of the device. One or more computing devices discussed hereinmay include some or all of the components discussed in FIG. 2, alongwith additional components.

The FIG. 2 example is a hardware configuration, although the illustratedcomponents may be implemented as software as well. Modifications may bemade to add, remove, combine, divide, etc. components of the computingdevice 200 as desired. Additionally, the components illustrated may beimplemented using basic computing devices and components, and the samecomponents (e.g., the processor 201, the ROM storage 202, the display206, etc.) may be used to implement any of the other computing devicesand components described herein. For example, the various componentsherein may be implemented using computing devices having components suchas a processor executing computer-executable instructions stored on acomputer-readable medium, as illustrated in FIG. 2. Some or all of theentities described herein may be software based, and may co-exist in acommon physical platform (e.g., a requesting entity can be a separatesoftware process and program from a dependent entity, both of which maybe executed as software on a common computing device).

One or more aspects of the disclosure may be embodied in acomputer-usable data and/or computer-executable instructions, such as inone or more program modules, executed by one or more computers or otherdevices. Generally, program modules include routines, programs, objects,components, data structures, etc. that perform particular tasks orimplement particular abstract data types when executed by a processor ina computer or other data processing device. The computer executableinstructions may be stored on one or more computer readable media suchas a hard disk, optical disk, removable storage media, solid statememory, RAM, etc. As will be appreciated by one of skill in the art, thefunctionality of the program modules may be combined or distributed asdesired in various embodiments. In addition, the functionality may beembodied in whole or in part in firmware or hardware equivalents such asintegrated circuits, field programmable gate arrays (FPGA), and thelike. Particular data structures may be used to more effectivelyimplement one or more aspects of the disclosure, and such datastructures are contemplated within the scope of computer executableinstructions and computer-usable data described herein.

FIG. 3 illustrates an exemplary wireless coverage map of multiplewireless access points in an area in accordance with one or moreillustrative aspects discussed herein. A mesh server 108 may generate awireless coverage map 300, which may include a geographical map of aparticular area (e.g., a neighborhood, retail center, business district,commercial or residential buildings, and the like). In this exemplaryembodiment, the wireless coverage map 300 is of a residentialneighborhood. The mesh server 108 may plot and/or otherwise illustrateon the map 300 multiple access points 305 a-l connected to multipleCMTSs 310 a-b via lines 320 a-b. The access points 305 a-l may beassociated with a particular service provider. Optionally, access points(e.g., residences) associated with a different service provider may alsobe shown on the map 300.

The mesh server 108 may plot and/or otherwise illustrate each of theaccess points 305 a-l on the map 300 at their approximate geographiclocations based on location information (e.g., latitude and longitude,GPS information, triangulation information, associated street address,and the like). The mesh server 108 may retrieve the location informationfrom one or more of a database of the central office 103 and/or mayreceive the location information from one or more of the access points305 a-l and/or another entity who provides location informationservices.

The mesh server 108 may determine a device type for each of the accesspoints 305 a-l. For example, when the service provider deploys devicesto access points 305 a-l, the service provider may log the device typein a database of the central office 103. Additionally or alternatively,in instances where either the device type is not stored in the database(e.g., because the user purchased the device and, thus, the serviceprovider did not deploy the device), the mesh server 108 may use SimpleNetwork Management Protocol (SNMP) or similar technology to identify thedevice type and/or may otherwise retrieve from the device it's devicetype (e.g., by sending a request to the device and receiving a responsefrom the device).

Once the device type is determined, the mesh server 108 may determinethe designed wireless range of each device (e.g., access points 305 a-l)by retrieving range information from a database of the central office orfrom another entity. For example, a first device type may have aneffective range of 200 feet while a second device type may have aneffective range of 100 feet. The mesh server 108 may plot and/orotherwise illustrate on the map 300 an initial estimated wirelesscoverage range 315 a-l (e.g., contours) for each access point 305 a-lbased on the designed wireless range of each device type. For example, acircular wireless range of 100 feet may be placed around one or theparticular access points (e.g., access point 305 d).

The mesh server 108 may account for the physical topography of eachparticular residence associated with each access point 305 a-l. Forinstance, the physical topography may include physical barriersincluding, for example, walls (e.g., concrete walls), floors, trees,other buildings or structures, signal interference, and the like. Thephysical barriers within the designed wireless range of the access point305 a-l may reduce the effective wireless range of that access point 305a-l in a particular direction. As a result, while the designed wirelessrange may be circular in shape, the effective wireless range might notbe circular in shape.

The mesh server 108 may determine the actual effective wireless ranges315 a-l (e.g., the true nature of the Wi-Fi signal emitting from theaccess points 305 a-l) through the use of network information providedby the access points 305 a-l. Particularly, the access points 305 a-lmay be wireless access points 305 a-l (e.g., Wi-Fi-enabled devices) inaccordance with wireless protocol (e.g., IEEE 802.11 standard). In orderto facilitate discovery of a particular access point (e.g., access point305 a) by other access points (e.g., access points 305 c-d) and/or otherwireless devices (e.g., signal detector, tablet, computer, cell phone,and the like), the particular access point (e.g., access point 305 a)may broadcast network information including a network identifier (e.g.,the public SSID provided by the service provider), network mode, and adevice identifier such as a medium access control (MAC) address of theparticular access point (e.g., access point 305 a).

One or more other access points (e.g., access points 305 c-d) and/orother wireless devices may receive the broadcast signal which may be abeacon signal at a particular signal strength depending on a variety offactors including distance from the broadcasting point, interference,and surrounding environment (e.g., buildings, objects, geographicalfeatures, elevation). The received signal strength of the broadcastsignal may be a received signal strength indication (RSSI) and may bedetermined by the access point receiving the broadcast signal. Thewireless access points 305 a-l may broadcast the beacon signals on thesame or different communication channels such as different frequencychannels. These channels may be channels defined by the IEEE 802.11standards. In some embodiments, other protocols may be used includinge.g., cellular protocols such as 3G, 4G, LTE, and the like. In someembodiments, the mesh server 108 may send an instruction to accesspoints 305 d-e within the designed range of access point 305 a. Theinstruction may request access points 305 d-e to determine whether theydetect access point 305 a via e.g., the public SSID and the associatedRSSI.

For example, access points 305 c-d located at neighboring residences mayreceive the broadcast network information from the access point 305 aand may send to the central office 103 the network information, the RSSIand their own respective identifier (e.g., a MAC address of accesspoints 305 c-d). In other words, the mesh server 108 may receive from atleast one access point an indication that the access point detected aparticular access point. In response, the central office 103 mayretrieve, e.g. from a database or entity, the location information(e.g., the address, latitude and longitude, etc.) of the access points305 a,c-d. The mesh server 108 may then refine the effective coveragerange 315 a of the access point 305 a based on the location informationof access points 305 a,c-d and the received RSSIs.

The access point 305 e might not detect access point 305 a. The accesspoint 305 e may send an indication to the mesh server 108 that accesspoint 305 e has not detected access point 305 a. The mesh server 108 mayfurther refine the effective coverage range 315 a of access point 305 abased on the location information of the access point 305 a and theaccess point 305 e.

In some embodiments, a technician of the service provider may, afterinstalling or servicing an access point 305 a, walk around the propertyof the user with a signal detector to receive the broadcasted networkinformation from the access point 305 a and may also determine locationinformation of the signal detector. The signal detector may create alocation-to-RSSI index. The signal detector may send the index to thecentral office 103. In some embodiments, the signal detector may sendthe network information received from the access point 305 a and theassociated location information of the signal detector to the centraloffice 103. The mesh server 108 may refine the map 300, in a mannersimilar to the above, based on the location of the signal detector, theRSSI, and the broadcast network information. Similarly, in someembodiments, a user of the service provider may walk down the streetwhile using a device (e.g., a cell phone or tablet) to stream contentfrom the service provider via a mobile app or a mobile web browser. Thedevice may snoop and/or otherwise detect access points 305 a-l (e.g.,Wi-Fi networks) that are within range of the device. The device mayreceive broadcast network information from the access points 305 a-l andmay determine associated RSSIs. The device may send to the mesh server108 the broadcast network information, RSSIs, and location informationof the device (e.g., determined by a GPS of the device). The mesh server108 may refine the map 300, in a manner similar to the above, based onthe location of the device, the RSSI, and the broadcast networkinformation.

In some embodiments, a mobile vehicle (e.g., a truck, mobile robot,etc.) may continuously or intermittently (e.g., periodically) snoop forSSIDs. For example, as the mobile vehicle travels within the effectiverange of access points 305 a-l, the mobile vehicle may receive broadcastnetwork information from one or more of the access points 305 a-l anddetermine associated RSSIs. The mobile vehicle may transmit to the meshserver 108 any detected broadcast network information and, optionally,the location information (e.g., GPS information) of the mobile vehicle.The mesh server 108 may refine the map 300 (e.g., wireless coverageranges 315 a-l) based on the location information of the mobile vehicleindexed with the broadcast network information and RSSIs for the one ormore access points 305 a-l.

Although the above discussed determining the effective wireless coveragerange 315 a of access point 305 a, the mesh server 108 may alsodetermine and refine the effective coverage ranges 315 b-l for each ofthe other access points 305 b-l in a similar manner.

The mesh server 108 may update the map 300 as information is receivedfrom one or more access points 305 a-l or devices (e.g., trucks,tablets, etc.). For example, the mesh server 108 may periodically sendrequests to neighboring access points (e.g., access points 305 c-e) todetermine whether those access points 305 c-e are within the effectivethe wireless coverage range 315 a of access point 305 a. Thus, any ofthe functions discussed above may be repeated to update the map 300 toaccount for e.g., a user moving the access point from the first floor ofhis residence to the basement of his residence, trees growing, buildingbeing erected, and the like.

Once the map 300 is generated, the mesh server 108 may use the map 300to identify overlaps in wireless coverage among the access points 305a-l. If the wireless coverage ranges between two access points overlap,the mesh server 108 may identify those two access points as being ablecommunicate with one another, for example, via the public SSID. Forexample, the wireless coverage range 315 a of access point 305 aoverlaps the wireless coverage range of 315 c of access points 305 c. Asa result, the mesh server 108 may identify access points 305 a,c asbeing able to communicate with one another. For example, consumerpremise devices (e.g., tablets, computers, etc.) connected to the accesspoint 305 a may communicate with the access point 305 c and consumerpremise devices connected to the access point 305 c and vice versa.

The mesh server 108 may use the map 300 to identify two access pointsthat might not directly overlap in wireless coverage but may overlap inwireless coverage via one or more intermediate access points. Forexample, the wireless coverage range 315 b of access point 305 b may notdirectly overlap with the wireless coverage range 315 k of access point315 k. However, the mesh server 108 may identify access point 305 b asbeing able to communicate with access point 315 k via intermediateaccess points 305 a,c-d,i. In such instances, the intermediate accesspoints 305 a,c-d,i may forward (e.g., relay or propagate) any receivedmessages. For example, the access point 305 c may receive a message fromthe access point 305 b and may forward the message to the access point305 a.

In some embodiments, the access points 305 a-k may be able to wirelesslycommunicate via the public SSID provided by the service provider.Additionally or alternatively, in some embodiments, the access points305 a-k may be able to wirelessly communicate by establishing a wirelessnetwork (e.g., a wireless ad hoc Wi-Fi network) via multiple privateSSIDs as will be discussed in more detail below. Further, the accesspoints 305 a-k and/or the mesh server 108 may send alert messages to oneor more of the access points 305 a-k and/or the mesh server 108 as willbe discussed in greater detail below in connection with FIG. 7.

The mesh server 108 may also use the map 300 to identify gaps inwireless coverage over a given area (e.g., in the residentialneighborhood). For example, if two portions of a neighborhood or twoneighborhoods are missing an access point between them, then the meshserver 108 may identify that gap and determine one or more options foreliminating that gap. For example, the mesh server 108 may identify afirst subset of the access points (e.g., access points 305 a-k). Themesh server 108 may identify a second subset of the access points (e.g.,access point 305 l) different from the first subset. Although the secondsubset of access points shows one access point, the second subset ofaccess points may include multiple access points with overlappingwireless coverage.

The mesh server 108 may identify a geographical gap in the wirelesscoverage between the first subset of access points 305 a-k and thesecond subset of access points 305 l. For example, the wireless coveragerange 315 l of the access point 305 l might not overlap with thewireless coverage range 315 g of the access point 305 g or the wirelesscoverage range 315 h of the access point 305 h. As a result, the meshserver 108 may identify access point 305 l as not being able tocommunicate with access points 305 a-k.

The mesh server 108 may determine one or more options to eliminate thegap. For example, the mesh server 108 may retrieve the device type ofeach of the access points 305 l,g-h in any manner discussed above. Themesh server 108 may determine the designed coverage range for each ofthe device types. The mesh server 108 may determine that switching oneor more of the devices at the access points 305 l,g-h to a differentdevice type with a wider designed coverage range may result in anoverlap coverage between the wireless coverage range 315 l of accesspoint 305 l and the wireless coverage range 315 g of access point 305 gand/or the wireless coverage range 315 h of access point 305 h.

In some exemplary embodiments, the mesh server 108 may determine that ifa new tower is placed at a particular location near (e.g., within apredefined distance) the access points 305 l,g-h, then the access point305 l may be able to communication with access point 305 g and/or accesspoint 305 h.

In some exemplary embodiments, the mesh server 108 may identify one ormore access points associated with a different service provider and/orone or more locations 102 (e.g., residences) that may become new accesspoints that would eliminate the gap in the wireless coverage. Forexample, the mesh server 108 may determine that a particular residencelocated between access point 305 h and access point 305 l(e.g., withinthe gap) may be able to eliminate the gap in coverage if that residenceis added as an access point with a particular device type. The serviceprovider may offer a discount to the owner or renter of that residenceto incentivize that owner or renter to subscribe to the serviceprovider. Thus, if residence becomes associated with a new access point,the gap in coverage may be eliminated and the map 300 may be updated bythe mesh server 108. Once the mesh server 108 determines the one or moreoptions to eliminate the gap in wireless coverage, the mesh server 108may alert an operator of the service provider.

In one or more embodiments, the mesh server 108 may increase (e.g.,boost) the bandwidth or data speed at a particular access point (e.g.,access point 305 c). For example, the mesh server 108 may increase thedata speed and/or bandwidth capacity provisioned for the access point305 c over a first distribution network (e.g., a first line 320 a). Insome embodiments, the mesh server may remove any data speed and/orbandwidth capacity limitations to the access point 305 c so that thedata speed and/or bandwidth may be the maximum speed and capacity of thefirst line 320 a. In some embodiments, the mesh server 108 may access aparticular access point through a neighboring access point to troubleshoot any problems at the particular access point.

Additionally or alternatively, the mesh server 108 may determine thataccess point 305 c may communicate with access point 305 f based on thegenerated wireless coverage map 300. Further, the mesh server 108 maydetermine that access point 305 c is connected to a first distributionnetwork (e.g., to the first CMTS 310 a via the first line 320 a) basedon the generated wireless coverage map 300. Similarly, the mesh server108 may determine that access point 305 f is connected to a seconddistribution network (e.g., to the second CMTS 310 b via the second line320 b) based on the generated wireless coverage map 300. The seconddistribution network may be different from the first distributionnetwork. The mesh server 108 may send to the access point 305 c and/orthe access point 305 f an instruction to establish a wireless network(e.g., a wireless ad hoc Wi-Fi network) between access point 305 c andaccess point 305 f. In response, the mesh server 108 may receive fromaccess point 305 c and/or access point 305 f an indication that thewireless network has been established.

The mesh server 108 might not use and/or otherwise send instructions toaccess points 305 a-b,d-e because each of those access points 305a-b,d-e is on the same line (e.g., the first line 320 a) as access point305 c. As a result, access points 305 a-e share bandwidth capacity anddata speed of the first line 320 a.

The mesh server 108 may provision the access point 305 c for aparticular bandwidth capacity and/or a particular data speed usingnetwork connectivity of both the first distribution network and thesecond distribution network. For example, the access point 305 c mayutilize the bandwidth and data speed of the second distribution networkvia the wireless connection established between the access point 305 cand access point 305 f. In other words, the mesh server 108 mayprovision the access point 305 c for a particular bandwidth capacityand/or a particular data speed by utilizing bandwidth and data speed ofthe first line 320 a and by utilizing additional bandwidth and dataspeed of the wireless connection to access point 305 f, which isobtained from the second line 320 b. In some embodiments, the meshserver 108 may provision the access point 305 c for a bandwidth capacityand/or a data speed beyond a maximum bandwidth capacity and/or dataspeed of the first line 320 a by obtaining at least some of thebandwidth and/or data speed from the wireless connection. In someembodiments, the mesh server 108 may send to the access point 305 cand/or the access point 305 f an instruction to increase provisionedbandwidth on the access point 305 c. The access point 305 c may receivea multiplexed service from both the first distribution network and thesecond distribution network and might not be limited to the physicalconstraints of the first distribution network. In other words, the meshserver 108 may coordinate with other servers 105-107 to multiplex thestream across the two distribution networks to the access point 305 c.In some embodiments, the access point 305 c may make the increasedbandwidth, data speed, and/or throughput available to one or more otheraccess points (e.g., access points 305 a,d-e).

While only two distributions networks (e.g., first line 320 a and secondline 320 b) are shown, more than two distribution networks mayprovisioned for use by the access point 305 c. In some embodiments,other access points may be provisioned for increased bandwidth and/ordata speed across multiple distribution networks in a similar manner asdiscussed above.

The mesh server 108 may initiate (e.g., trigger) the increase inbandwidth for the access point 305 c based on a comparison ofcharacteristics of the distribution networks. For example, when thefirst distribution network is heavily congested (e.g., above apredetermined threshold) resulting in lower bandwidth (e.g., below apredetermined threshold) and/or a lower data speed (below apredetermined threshold) as compared to the second distribution networkwhich may be less utilized, the mesh server 108 may increase bandwidthavailable to the access points on the first distribution network bybridging via a wireless connection to access points of the seconddistribution network.

In some embodiments, the wireless connections may enable the serviceprovider to provide service to one or more access point not directlyconnected to a distribution network. For example, the wirelessconnection may be used to get new homes connected to the local office103 more quickly (e.g., before they are connected to lines 101 a).

FIG. 4 illustrates a flowchart of an exemplary method for detectingtheft of service in accordance with one or more illustrative aspectsdiscussed herein. In one or more embodiments, the method of FIG. 4and/or one or more steps thereof may be performed by a computing device(e.g., computing device 200). In other embodiments, the methodillustrated in FIG. 4 and/or one or more steps thereof may be embodiedin computer-executable instructions that are stored in acomputer-readable medium, such as a non-transitory computer-readablememory.

As seen in FIG. 4, the method may begin at step 405 in which a scanningdevice may scan for SSIDs (e.g., public SSIDs and private SSIDs providedto users) and MAC address of access points and/or devices connected tothe access points (e.g., tablets, computers, cell phones, and the like).For example, in step 405, the scanning device may be, for example, aneighboring access point having overlapping wireless coverage with aparticular access point, a mobile vehicle (e.g., a truck of the serviceprovider), or any other computing device. In some instances, aneighboring access point may continuously or intermittently (e.g.,periodically) detect one or more of a public SSID, a private SSID, andor an emergency SSID broadcast from the particular access point. Theneighboring access point may send a request for a MAC address of eachdevice associated (e.g., connected) with the particular access pointand, in response, may receive one or more MAC addresses of variousdevices. The neighboring access point may send to the mesh server 108the received one or more MAC addresses, the SSID, and an identifier ofthe neighboring access device. The neighboring access point may send theinformation to the mesh server 108 via the one or more links 101 and/orvia a wireless connection with one or more access points. In someembodiments, the neighboring access point may determine and send to themesh server 108 the location information (e.g., GPS coordinate) of theneighboring access point. Additionally or alternatively, in someembodiments, the mesh server 108 may obtain the location information ofthe neighboring access point by retrieving the locations from a databaseof the central office 103.

In some exemplary embodiments, a mobile vehicle of the service providermoving along a route may continuously scan for SSIDs and MAC addressesas its wireless coverage range temporarily overlaps the wirelesscoverage range of the particular access point along the route. Similarto the neighboring access point discussed above, the mobile vehicle maysend a request for SSIDS and/or MAC addresses and, once received fromthe particular access point, may send to the mesh server 108 the SSIDsand MAC addresses associated with the particular access point and thelocation information of the mobile vehicle (e.g., determined by a GPSwithin the mobile vehicle).

In step 410, the mesh server 108 may obtain estimated locationinformation for the particular access point. For example, in step 410,the mesh server 108 may estimate the geographic location of theparticular access point and/or devices connect to the particular accesspoint based on the location information of one or more of theneighboring access point, the mobile vehicle, and/or any other computingdevice (e.g., other access points). For example, the mesh server 108 mayretrieve the location information of the neighboring access point from adatabase of the central office 103. The mesh server 108 may retrievelocation information of the mobile vehicle from a database of thecentral office 103 and/or may receive the location information from themobile vehicle itself. The mesh server 108 may then, using the generatedmap (e.g., wireless coverage map 300), estimate the geographic locationof the particular access point. In instances where mesh server 108receives SSIDs, MAC addresses, and/or other identifiers from multipleneighboring access points or from a mobile vehicle and a neighboringaccess point, the mesh server 108 may use any known triangulation methodto estimate the geographic location of the particular access point.

In step 415, the mesh server 108 may obtain the user's locationinformation. For example, in step 415, the mesh server 108 may, usingthe received MAC address and/or SSIDs, lookup and/or otherwise retrievethe user's location information from a database of the central office103. The user's location information may include a previously determinedgeographic location for the particular access point.

In step 420, the mesh server 108 may compare the estimated geographiclocation of the particular access point with the user's locationinformation (e.g., the pre-stored geographic location of the accesspoint of the user). For example, in step 420, the mesh server 108 maycompare the estimated latitude and longitude, the associated address,and/or GPS coordinates of the particular access point with thepre-stored latitude and longitude, the associated address, and/or GPScoordinates of the access point of the user. In some embodiments, theparticular access point and the access point of the user may behighlighted on the map 300 in different colors.

In step 425, the mesh server 108 may determine whether the estimatedgeographic location matches the user's location information. Forexample, in step 425, the mesh server 108 may determine that there maybe a match when the estimated geographic location is within a predefinedor user-specified geographic distance of the pre-stored geographiclocation. Similarly, the mesh server 108 may determine that there mightnot be a match when the estimated geographic location is outside of apredefined or user-specified geographic distance of the pre-storedgeographic location. In response to a determination that the estimatedgeographic location matches the particular known (e.g., pre-stored)geographic location, the method may end. In response to a determinationthat the estimated geographic location does not match the particularknown geographic location, the method may proceed to step 430.

In step 430, the mesh server 108 may flag the user's account and eitherupdate the pre-stored geographic location or discontinue service to oneor more of the received MAC address. For example, in step 430, the meshserver 108 may flag the user's account to an operator of the serviceprovider. The mesh server 108 may, in response to receiving anindication that the device associated with the MAC address is in thecorrect geographic location, update the user's location information inthe database. The mesh server 108 may, in instances where the deviceassociated with the MAC address in in the incorrect geographic location,identify the device associated with the MAC address and/or theparticular wireless access point as unauthorized. The mesh server 108may block or discontinue service to the device associated with that MACaddress and/or to the particular access point.

In some embodiments, the mesh server 108 may receive a MAC address of anaccess point (e.g., a first access point) from the access point and/orother access points that detected the access point. The mesh server 108may determine an estimated geographic location of the MAC address basedon the generated map. The mesh server 108 may compare the estimatedgeographic location with the user's location information (e.g., thegeographic location of access point stored in a database of theheadend). If the estimated geographic location and the stored geographicinformation are not within a predefined distance, the mesh server 108may compare the MAC address with another detected and/or received MACaddress of another access point (e.g., a second access point). If theMAC address match, the mesh server 108 may identify and/or flag thefirst access point as being a potentially unauthorized access pointspoofing the second access point.

FIG. 5 illustrates an exemplary system for connecting a wireless networkin accordance with one or more illustrative aspects discussed herein.The system 500 may include a first CMTS 505 a connected to access point515 a via a first line 510 a. The system 500 may include a second CMTS505 b connected to access points 515 b-k via a second line 510 b. Thefirst CMTS 505 a and/or the first line 510 a may be referred to as afirst distribution network. The second CMTS 505 b and/or the second line510 b may be referred to as a second distribution network.

A failure or a loss in network connectivity at portion(s) of thedistribution network(s) may result in one more access points (e.g.,access points 515 a-k) losing network connectivity with the centraloffice 103 over their respective distribution network (e.g., a CMTSand/or a line). In some instances, the failure may be caused by anatural disaster, an accident, an attack, construction, or any otherevent. For example, a CMTS (e.g., the second CMTS 505 b) may bedestroyed or may be temporarily unavailable after an earthquake. Forexample, a line (e.g., the second line 510 b) may have been accidentallycut during construction of a new building. In either instance, one ormore access points 515 b-k may lose network connectivity with the secondCMTS 505 b due to e.g., a cut in the second line 505 b or because thesecond CMTS 505 b is unavailable.

In such instances, the mesh server 108 may initiate a process toestablish a wireless network between the multiple access points 515 a-kto maintain service to those access points 515 a-k as will be discussedin further detail in FIG. 6 below. In other words, rather than using thesecond line 510 b, an access point (e.g., access point 515 g) mayestablish a wireless network connection with a series of access points515 a,c,f until the wireless connection reaches an access point 515 athat has network connectivity back to a headend device (e.g., the firstCMTS 505 a). More specifically, as discussed above in FIG. 3, one ormore of the access points 515 a-k may have overlapping coverage areasenabling the access points 515 a-k to communicate with one anotherwirelessly (e.g., via Wi-Fi bridging). The access points 515 a-k mayinitiate communications with one another via a public SSID provided bythe service provider send to each of the access points 515 a-k.Thereafter, the access points 515 a-k may initialize their own privateSSIDs (e.g., private SSID1-5) to establish a wireless network (e.g., awireless ad hoc Wi-Fi network) for use with future communications. Insome embodiments, the access points 515 a-k may communicate with anotherby using an emergency broadcast SSID different from the public SSID andthe private SSIDs1-5. In such embodiments, each access point 515 may bepreconfigured to use the emergency SSID when that access point 515 losesnetwork connectivity with the headend device, for example, over thelines 510 a-b.

In some embodiments, the mesh server 108 may initiate the process toestablish a wireless network between the multiple access points 515 a-keven in instances where there might not have been any connectivity loss(e.g., the second CMTS 505 b and the second line 510 b may be fullyoperational and providing network connectivity to the access points 515b-k. For example, the mesh server 108 may establish the wireless networkto one or more designated access points, using a generated coverage map,to increase bandwidth and/or data speed to one or more particular accesspoints as discussed above in FIG. 3.

While two CMTSs 505 a-b are shown, there may be more than two CMTSs.Additionally, while each of the access points 515 b-k have lost networkconnectivity, in some embodiments, some of the access points (e.g.,access points 515 b and 515 i) may have network connectivity while theother access points (e.g., access points 515 c, 515 d-h,j-k) may havelost network connectivity.

FIG. 6 illustrates a flowchart of an exemplary method for establishing awireless network in accordance with one or more illustrative aspectsdiscussed herein. In one or more embodiments, the method of FIG. 6and/or one or more steps thereof may be performed by a computing device(e.g., computing device 200). In other embodiments, the methodillustrated in FIG. 6 and/or one or more steps thereof may be embodiedin computer-executable instructions that are stored in acomputer-readable medium, such as a non-transitory computer-readablememory.

As seen in FIG. 6, the method may begin at step 605 in which a firstaccess point (e.g., access point 515 a) may receive from a core (e.g., aheadend device such as the first CMTS 505 a) a mesh initiation packetvia a public SSID of the service provider provided to the access points515 a-k. In this exemplary embodiment, the second distribution networkincluding the second CMTS 505 b may be temporarily unavailable. As aresult, the first CMTS 505 a might not be able to send the meshinitiation packet to access points 515 b-k because access points 515 b-kmay have lost network connectivity with the first CMTS 505 a.

The mesh initiation packet may include a join emergency mesh (JEM)message. The JEM message may include instructions and/or a protocol tobuild the wireless network (e.g., an ad hoc wireless network) among theaccess points 515 a-k. For example, the JEM message may instruct each ofthe access points 515 a-k to create or initiate a private SSID for usewith the wireless network and/or may instruct the access point to use anemergency SSID. The JEM message may instruct each of the access points515 a-k to broadcast the JEM message and their respective privateSSID1-5 using the public SSID. In some embodiments, the JEM message mayspecify which access points the JEM message is to be sent. In someembodiments, the JEM message may include identifiers of access pointsthat have lost their network connectivity to the headend device.

In step 610, an access point 515 a with network connectivity to theheadend may broadcast the JEM message and its private SSID using thepublic SSID provided by the service provider. For example, in step 610,in response to receiving the mesh initiation packet, access point 515 amay initialize (or initiate use of) its private SSID1. The private SSID1may be created locally by the access point 515 a, or the access point515 a may have received the private SSID1 at some point from the headenddevice and stored the private SSID1 in network storage of access point515 a. Because the access point 515 a may have an overlapping coveragearea with access points 515 c,d, the access points 515 c,d may receive,using the public SSID, the broadcasted JEM message and private SSID1from the access point 515 a.

As a result of receiving the private SSID1 from the access point 515 a,the access points 515 c and 515 d may establish a wireless connectionwith access point 515 a to receive service (e.g., a transport stream)from a headend device through access point 515 a. More specifically, theaccess point 515 a may receive the transport stream from the first CMTS505 a and may forward the transport stream to the access points 515 c-dover the wireless network (i.e., the emergency communication mesh) usingprivate SSID1. Further, access points 515 c-d may transmit requestsupstream to the first CMTS 505 a. For example, the access points 515 c-dmay transmit requests to the access point 515 a over the wirelessnetwork using private SSID1 and the access point 515 a may forward therequest to the first CMTS 505 a via the first link 510 a.

In step 615, if an access point does not have network connectivity tothe headend device, then the access point may initialize its own privateSSID. For example, in step 615, after receiving the JEM message, theaccess point 515 c may determine that it does not have networkconnectivity to the second CMTS 505 b and may, in response, initialize(or initiate use of) its private SSID2. The private SSID2 may be createdlocally by the access point 515 c, or the access point 515 c may havereceived private SSID2 at some point from the headend device and storedthe private SSID2 in network storage of access point 515 c.

Similarly, after receiving the JEM message, the access point 515 d maydetermine that it does not have network connectivity to the second CMTS505 b and may, in response, initialize private SSID4. In someembodiments, the access point 515 c may send its private SSID2 to theaccess point 515 a. Similarly, in some embodiments, the access point 515d may send its private SSID4 to the access point 515 a.

In step 620, the access point may broadcast its private SSID and the JEMmessage to the next access point using the public SSID. For example, instep 620, the access point 515 c may have an overlapping coverage areawith access points 515 b,f. Thus, the access points 515 b,f may receive,using the public SSID, the broadcasted JEM message and the private SSID2from the access point 515 c. As a result of receiving the private SSID2from the access point 515 c, the access points 515 b,f may establish awireless connection with the access point 515 c to receive service(e.g., a transport stream) from the headend device through the accesspoints 515 a,c. More specifically, the access point 515 a may receivethe transport stream from the first CMTS 505 a and may forward thetransport stream to the access point 515 c over the wireless network(i.e., the emergency communication mesh) using private SSID1. The accesspoint 515 c may then forward the transport stream to the access point515 b using the private SSID2. The access point 515 b may send a requestto the first CMTS 505 a. For example, the access point 515 b may sendthe request to the access point 515 c using private SSID2, access point515 c may forward the request to access point 515 a using private SSID1,and the access point 515 a may send the request to the first CMTS 505 avia the first link 510 a. The access point 515 f may receive thetransport stream and send requests in a similar manner.

In step 625, if the next access point does not have network connectivityto the headend device, then the next access point may initialize its ownprivate SSID and may broadcast the private SSID and the JEM message toanother access point using the public SSID. For example, in step 625,after receiving the JEM message, the access point 515 f may determinethat it does not have network connectivity to the second CMTS 505 b andmay, in response, initialize private SSID3. The access point 515 f maybroadcast the private SSID3 and the JEM message to the next access pointusing the public SSID. For example, the access point 515 f may have anoverlapping coverage area with access points 515 g-h. Thus, the accesspoints 515 g-h may receive, using the public SSID, the broadcasted JEMmessage and the private SSID3 from the access point 515 f.

Similarly, after receiving the JEM message, the access point 515 i maydetermine that it does not have network connectivity to the second CMTS505 b and may, in response, initialize private SSID5. The access point515 i may broadcast the private SSID5 and the JEM message to the nextaccess point using the public SSID. For example, the access point 515 imay have an overlapping coverage area with access points 515 j-k. Thus,the access points 515 j-k may receive, using the public SSID, thebroadcasted JEM message and the private SSID5 from the access point 515i.

Step 625 may be repeated until there are no more access points with anoverlapping coverage with any of the access points 515 a-k. Thus, theaccess points 515 a-k that are each a part of the emergencycommunication mesh (e.g., the ad hoc wireless network). By using thewireless network, access points 515 a-k may continue to provide serviceto users' of the service provider even when access points 515 b-k losenetwork connectivity to the second CMTS 505 b.

Referring back to FIG. 5, each of the access points 515 a-k mayinstantiate a dynamic host configuration protocol (DHCP) and/or someother protocol so that each of the access points 515 a-k may become aserver for other connected access point 515 a-k. Each of the accesspoints 515 a-k may act as a proxy for other connected access points 515a-k to create an ad hoc routing tree.

The access point 515 a may be connected to the first CMTS 505 a andaccess points 515 b-k may be connected to the second CMTS 505 b. Inother words, the access point 515 a may be assigned to the first CMTS505 a and the access points 515 b-k may be assigned to the second CMTS505 b. As a result of the emergency communication mesh, in someembodiments, one or more access points 515 b-k assigned to the secondCMTS 505 b may be connected to and may communicate with the first CMTS505 a (instead of or in addition to the second CMTS 505 b).Particularly, the one or more access points 515 b-k may communicate withfirst CMTS 505 a through one or more intermediate access pointsincluding, for example, the access point 515 a.

In one or more embodiments, in response to a determination by one ormore of the access points 515 b-k that the one or more access points 515b-k has network connectivity to the headend device over the seconddistribution network (e.g., has regained network connectivity to thesecond CMTS 505 b via the second line 510 b), those particular accesspoints may send an indication of such network connectivity to the meshserver 108 using the emergency communication mesh and/or the seconddistribution network. The mesh server 108 may identify those accesspoints as egress access points and may initiate a process to establishone or more additional wireless networks different from the firstwireless network by sending to those egress access points the meshinitiation packet. In some embodiments, the mesh initiation packet mayspecify which access points may connect to the respective wirelessnetwork. In some embodiments, the mesh server 108 might not identify oneof those particular access points as an egress access point becausealthough that particular access point may have detected that it hasregained network connectivity to e.g., a CMTS, there may be a fiber cutor connectivity lost at some point upstream from that CMTS. As a result,even if that particular access point connected with that CMTS, theparticular access point might not receive service. In such embodiments,the mesh server 108 may send to the particular access point aninstruction to continue to use the emergency communication mesh and notits assigned distribution network. The mesh server 108 may send theinstruction to the particular access point via an egress access pointand the emergency communication mesh. Accordingly, the particular accesspoint may continue to use the wireless network even after the particularaccess point establishes network connectivity to its assigned CMTS(e.g., a headend device).

In one or more embodiments, an emergency mesh network may be createdusing a repetitive discovery protocol. In such embodiments, while thedistribution networks were functioning (e.g., when the access points 515a-k had network connectivity to the headend device over their respectivedistribution networks), the mesh server 108 may distribute the emergencymesh network plan to the access points 515 a-k. In other words, the meshserver 108 may send to the access points 515 a-k an instruction to,after a loss of connectivity for a predetermined period of time,periodically interrogate whether a geographically adjacent access pointhas a connection to a headend device (e.g., through the emergencywireless mesh network), and connect to the geographically adjacentaccess point (e.g., by bridging Wi-Fi connections) once thatgeographically adjacent access point establishes a connection to thehead device.

The emergency mesh network plan may identify, for each of the accesspoints 505 a-k, one or more of the other access points 515 a-k toconnect to in the event of a network outage. The emergency mesh networkplan may specify for a particular access point (e.g., access point 515f) an order of the neighboring access points 515 c,g-h with which toattempt connecting in order to connect to the emergency mesh network.For example, the emergency mesh network plan may specify that accesspoint 515 f may first attempt to connect to access point 515 c. If theaccess point 515 f is unable to connect to the emergency mesh networkafter waiting a predetermined period of time, then the emergency meshnetwork plan may specify that access point 515 f may next attempt toconnect to the access point 515 h in an attempt to connect to theemergency mesh network.

In some instances, if the access point 515 f loses network connectivityto the headend device (e.g., the second CMTS 505 b), the access point515 f may wait for a predetermined period of time. If the access point515 f has not regained network connectivity after the predeterminedperiod of time has expired, then the access point 515 f may, using theemergency mesh network plan, connect to assigned neighboring accesspoints (e.g., access point 515 c and access point 515 h) using either apublic SSID and/or an emergency backup SSID. Specifically, the accesspoint 515 f may send to access point 515 c a request inquiring whetherthe access point 515 c has network connectivity to a headend deviceeither directly through its assigned distribution network or indirectlythrough the emergency mesh network. In response to receiving anindication from the access point 515 c that access point 515 c does nothave network connectivity to a headend device or after waiting apredetermined period of time, the access point 515 f may send to accesspoint 515 h a request inquiring whether the access point 515 h hasnetwork connectivity to a headend device either directly through itsassigned distribution network or indirectly through the emergency meshnetwork. In response to receiving an indication from access point 515 hthat access point 515 h does not have network connectivity to a headenddevice or after waiting a predetermined period of time, the access point515 f may, using the emergency mesh network plan, connect to any otherspecified and/or detected access point to attempt to connect to theemergency mesh network. In response to a determination that the accesspoint 515 f has been unable to connect to the emergency mesh network andafter a predetermined period of time has expired, the access point 515 fmay retry connecting to the emergency mesh network in a similar manneras discussed above.

As a result of each of the access points 515 b-k attempting to connectto the emergency mesh network using the repetitive discovery protocol,the emergency mesh network may eventually connect each of the accesspoints 515 a-k with a headend device. For example, the first time eachof the access points 515 b-k attempts to connect to the emergency meshnetwork, access points 515 c-d may connect to the emergency wirelessnetwork. The next time each of the remaining access points 515 b,e-kattempts to connect to the emergency mesh network, access points 515b,e-f,i may connect to the emergency wireless network. The next timeeach of the remaining access points 515 g-h,j-k attempts to connect tothe emergency mesh network, each of the remaining access points 515g-h,j-k may connect to the emergency mesh network.

In one or more embodiments, an access point that has lost networkconnectivity may initiate an emergency communication mesh after apredetermined time period has expired. For example, an originatingaccess point (e.g., access point 515 g) may have received from a headenddevice a JEM message, an emergency backup SSID, and/or one or moredesignated neighboring access points to connect to in the event of anoutage. In some embodiments, the originating access point 515 g maygenerate the JEM message. The JEM message may include an identifier ofthe originating access point 515 g and an indication that the originatedaccess point 515 g does not have network connectivity to a headenddevice. In response to a determination that the originating access point515 g has lost network connectivity to the headend device via itsassigned distribution network, the originating access point 515 g maysend to the one or more designated neighboring access points (e.g.,access point 515 f) a JEM message and its private SSID (e.g., a firstprivate SSID) by using either a public SSID of the service provider orthe emergency backup SSID. In instances where there the originatingaccess point 515 g might not have designated neighboring access points,the originating access point 515 g may detect and/or otherwise discoverany neighboring access points with which it has an overlapping coveragearea and may send the JEM message and the first private SSID to thoseneighboring access points (e.g., access point 515 f).

In response to receiving the JEM message and the first private SSID, awireless network may be established between the originating access point515 g and the neighboring device 515 f using the first private SSID. Theneighboring access point 515 f may determine whether it has networkconnectivity to a headend device either directly through its assigneddistribution network or indirectly through a wireless network. If theneighboring access point 515 f does not have any network connectivity,then the neighboring device 515 f may increase a hop count included inthe JEM message and add to the JEM message its own identifier and anindication that the neighboring access point does not have networkconnectivity to the headend device. Additionally, the neighboring accesspoint 515 f may initialize its own private SSID (e.g., a second privateSSID) and may broadcast the JEM message and the second private SSID toeither designated access points and/or detected access points.

The process may continue to repeat adding one or more additionalintermediate neighboring points (e.g., access point 515 c) extending thewireless network until the JEM message is received by an egress accesspoint (e.g., access point 515 a that still has network connectivity overits assigned distribution network and/or an access point that is part ofa wireless network where at least one access point has networkconnectivity over its assigned distribution network). At that point, theegress access point 515 a may forward communications between the headenddevice and the one of the intermediate neighboring points 515 c, andthose points may forward communications to other access points. As aresult, the originated access point 515 g, its neighboring access point515 f, the one or more additional intermediate access points 515 c, theegress access point 515 a, and the headend device may each communicatewith one another.

FIG. 7 illustrates an exemplary system for optimizing a wireless networkin accordance with one or more illustrative aspects discussed herein.The system 700 may include access points 705 a-k connected via one ormore lines (not shown) to a headend device (not shown). The accesspoints 705 a-b may have network connectivity to the headend devicethrough one or more distribution networks as discussed herein. Theaccess points 705 a-b may also be referred to as egress access points.The access points 705 c-k might not have network connectivity to theheadend device through the one or more distribution networks.

FIG. 8 illustrates a flowchart of an exemplary method for optimizing awireless network in accordance with one or more illustrative aspectsdiscussed herein. In one or more embodiments, the method of FIG. 8and/or one or more steps thereof may be performed by a computing device(e.g., computing device 200). In other embodiments, the methodillustrated in FIG. 8 and/or one or more steps thereof may be embodiedin computer-executable instructions that are stored in acomputer-readable medium, such as a non-transitory computer-readablememory.

As seen in FIG. 8, the method may begin at step 805 in which a meshserver 108 and/or one or more access points 705 a-k may detect a networkfailure. For example, in step 805, the network failure may be the resultof a disaster, attack, accident, or the like. The network failure may bea loss of network connectivity to one or more portions of the network(e.g., the HFC lines) of the service provider. The mesh server 108and/or one or more access points 705 a-k may detect a network failureby, for example, receiving an indication of a network failure fromanother device or a user, detecting a loss of network connectivity for apredetermined period of time, etc.

In step 810, the mesh server 108 may identify adjacent access points andegress access points. For example, the mesh server 108 may identifyadjacent access points by using a generated wireless coverage map (asdiscussed above in FIG. 3) and identifying those access points that havean overlapping wireless coverage area as adjacent access points. Forexample, access point 705 a may be identified as adjacent to accesspoint 705 d when access point 705 a and access point 705 d have anoverlapping wireless coverage area. The mesh server 108 may alsoidentify egress access points 705 a-b using the generated wirelesscoverage map and sending requests to verify network connectivity to onemore access points 705 a-k. In response, the mesh server 108 may receivefrom the egress access points 705 a-b a verification message that theegress access points 705 a-b have network connectivity with the headenddevice via one or more distribution networks (e.g., a DOCSIS network).The mesh server 108 might not receive a verification message from theaccess points 705 c-k when access points 705 c-k have lost networkconnectivity with the headend device via the one or more distributionnetworks.

In step 815, the mesh server 108 may send a JEM message to a respectiveone or more of the egress access points 705 a-b. For example, a firstJEM message may include instructions for the egress access points 705 ato begin establishing an emergency mesh network (e.g., a Wi-Fi bridgingnetwork). The first JEM message may designate which access points 705a-k and in what order the first JEM message is to be sent or forwardedto those access points 705 a-k. Similarly, the mesh server 108 may sendto egress access point 705 b a second JEM message different from thefirst JEM message. The second JEM message may be configured in a similarmanner as the first JEM message.

In step 820, the mesh server 108 may provision the fastest class ofservice to the egress access points 705 a-b and any other configurationelements. For example, in step 820, the mesh server 108 may remove anybandwidth capacity, data speed, and/or throughput limitations fromegress access points 705 a-b. Consequently, the egress access points 705a-b may be provisioned to utilize a maximum bandwidth, data speed,and/or throughput of the one or more distribution networks (e.g., theHFC lines). The other configuration elements may include dedicating morerouters in the backplane to a CMTS connected to the egress access points705 a-b. These routers may route transit data between the CMTS and theegress access points 705 a-b.

In step 825, the egress access points 705 a-b may each respectivelyinitialize a private SSID and respectively broadcast the JEM message,the private SSIDs, and a hop-count using the public SSID. For example,in step 825, the egress access point 705 a may initialize its ownprivate SSID by either locally generating the private SSID or retrievingit from network storage. The egress access point 705 a may broadcast thefirst JEM message, its own private SSID, and a first hop-count using thepublic SSID provided by the service provider. The egress access point705 a may broadcast this information either to access points specifiedin the first JEM message (e.g., access point 705 d) and/or a detectedaccess point (not shown). A detected access point may be any accesspoint having an overlapping wireless coverage range with the egressaccess point 705 a, thereby enabling wireless communication between thedetected access point and the egress access point 705 a.

Similarly, the egress access point 705 b may initialize its own privateSSID by either locally generating the private SSID or retrieving it fromnetwork storage. The egress access point 705 b may broadcast the secondJEM message, its own private SSID, and a second hop-count using thepublic SSID provided by the service provider. The egress access point705 b may broadcast this information to the access points specified inthe second JEM message (e.g., access point 705 g) and/or a detectedaccess point (not shown).

In step 830, one or more emergency wireless meshes may be establishedand next access points (e.g., access point 705 d,g) may initialize theirown private SSID and may each increment their respective hop-count. Forexample, in step 830, the access point 705 d may receive from the egressaccess point 705 a the first JEM message, the first hop-count, and theprivate SSID of the egress access point 705 a using the public SSID. Afirst emergency wireless mesh (e.g., a first ad hoc wireless network)may be established by bridging the wireless (e.g., Wi-Fi) connections ofthe egress access point 705 a and the access point 705 d. The egressaccess point 705 a and the access point 705 d may communicate with oneanother using the private SSID of the egress access point 705 a. Theaccess point 705 d may initialize its own private SSID by either locallygenerating the private SSID or retrieving it from network storage. Theaccess point 705 d may increment the first hop-count by one (e.g., fromzero to one hop).

Similarly, the access point 705 g may receive from the egress accesspoint 705 b the second JEM message, the second hop-count, and a privateSSID of the egress access point 705 b using the public SSID. A secondemergency wireless mesh (e.g., a second ad hoc wireless network) may beestablished by bridging the wireless (e.g., Wi-Fi) connections of theegress access point 705 b and the access point 705 g. The secondemergency mesh may be different from the first emergency mesh. Theegress access point 705 b and the access point 705 g may communicatewith one another using the private SSID of the egress access point 705b. The access point 705 g may initialize its own private SSID by eitherlocally generating the private SSID or retrieving it from networkstorage. The access point 705 g may increment the second hop-count byone (e.g., from zero to one hop).

In step 835, the access points 705 d,g may broadcast their respectiveJEM message, hop-count, and private SSID. For example, in step 835, theaccess point 705 d may broadcast the first JEM message, the firsthop-count, and the private SSID of the access point 705 d. The accesspoint 705 d may broadcast this information to the access pointsspecified in the first JEM message (e.g., access point 705 c) and/or adetected access point (e.g., access point 705 e), using the public SSIDprovided by the service provider. The first JEM message may specifywhether to connect to a detected access points or designated accesspoints.

Similarly, the access point 705 g may broadcast the second JEM message,the second hop-count, and the private SSID of the access point 705 g.The access point 705 g may broadcast this information to the accesspoints specified in the second JEM message (e.g., access point 705 i)and/or a detected access point using the public SSID provided by theservice provider. The second JEM message may specify whether to connectto a detected access points or designated access points.

In step 840, the one or more emergency meshes may be expanded and thenext access points may initialize their own private SSID and incrementtheir respective hop-count. For example, in step 840, the access points705 c,e may receive the first JEM message, the first hop-count, and theprivate SSID of the access point 705 d. The first emergency mesh may beexpanded (e.g., joined) by bridging the wireless (e.g., Wi-Fi)connections of the access point 705 d and the access point 705 e. Theaccess point 705 d and the access point 705 e may communicate with oneanother using the private SSID of the access point 705 d. The firstemergency mesh may be expanded by bridging the wireless connections ofthe access point 705 d and the access point 705 c. The access point 705d and the access point 705 c may communicate with one another using theprivate SSID of the access point 705 d. The access point 705 c mayinitialize its own private SSID and may increment the first hop-count byone (e.g., from one to two hops). The access point 705 e may alsoinitialize its own private SSID and may increment the first hop-count byone (e.g., from one to two hops).

Similarly, the access points 705 i may receive the second JEM message,the second hop-count, and the private SSID of the access point 705 g.The second emergency mesh may be expanded (e.g., joined) by bridging thewireless (e.g., Wi-Fi) connections of the access point 705 g and theaccess point 705 i. The access point 705 g and the access point 705 imay communicate with one another using the private SSID of the accesspoint 705 g. The access point 705 i may initialize its own private SSIDand may increment the second hop-count by one (e.g., from one to twohops).

In step 845, the access points may optionally switch connections tooptimize the one or more emergency meshes. For example, in step 845,each access point that has lost connectivity through its distributionnetwork and that is a part of an emergency mesh may evaluate any otheremergency meshes to determine whether that access point should switch toanother emergency mesh. For example, the access point 705 e may receivea JEM message, hop-count, and a private SSID from one of the accesspoints of the other emergency meshes (e.g., a third emergency mesh). Theaccess point 705 e may increment the hop-count received from the thirdemergency mesh and may compare that hop-count with the first hop countassociated with the first emergency mesh. If the first hop-count islower than the hop-count associated with the third emergency mesh, theaccess point 705 e may maintain its current connection to the firstemergency network. If the first hop-count is greater than the hop-countassociated with the third emergency mesh, the access point 705 e maydisconnect from its current emergency mesh and join the other emergencymesh via another access point. The access point 705 e may also switchemergency meshes based on, for example, the other emergency mesh havinga greater bandwidth, higher data speed, greater throughput, and thelike.

In step 850, the access point 705 e,i may broadcast their respective JEMmessage, hop-count, and private SSID in a similar as discussed abovee.g., in step 835. The steps 840-850 may be repeated until each of theaccess points 705 a-k are a part of an emergency mesh.

In an exemplary embodiment, the access point 705 h may, in step 840,receive from the access point 705 e the first JEM message, the firsthop-count and a private SSID of the access point 705 e. The access point705 h may, in step 840, expand (e.g., join) the first emergency mesh bybridging the wireless (e.g., Wi-Fi) connections of the access point 705e and the access point 705 h. The access point 705 h may increment thefirst hop-count by one (e.g., from two to three hops). At a later time,the access point 705 h may, in step 840, receive from access point 705 gthe second JEM message, the second hop-count and a private SSID of theaccess point 705 g. The access point 705 h may increment the secondhop-count by one (e.g., from one to two hops). In step 845, the accesspoint 705 h may compare the first hop-count and the second hop-count.Because the second hop-count (e.g., two hops) is less than the firsthop-count (e.g., 3 hops), the access point 705 h may disconnect from thefirst emergency mesh (i.e., disconnecting from access points 705a,c-d,e-f) and may connect to (e.g., join) the second emergency mesh(i.e., 705 b,g,i-k) by bridging its wireless connection with thewireless connection of access point 705 g.

Referring back to FIG. 7, the access point 705 h may also switchemergency meshes based on, for example, the second emergency mesh havinga greater bandwidth, higher data speed, and/or greater throughput thanthat of the first emergency mesh. In some embodiments, the access point705 h may switch emergency meshes based on a least distance routingalgorithm associated with shortest path back to a headend device (e.g.,a CMTS). In some embodiments, the access point 705 h may switchemergency meshes based on an open shortest path first (OSPF) algorithm,a border gateway protocol (BGP) algorithm, a hop-count trace routingprotocol, or the like. The access point 705 a-k may be configured to useone or more of the above algorithms or may receive signals to implementsuch algorithms. In some embodiments, an access point (e.g., the accesspoint 705 e) may receive a signal indicating that service has beenrestored to the access point 705 f along with instructions to connect tothe access point 705 f for service.

In some embodiments, the access point 705 h might not switch to thesecond emergency mesh even if it would result in a lower hop-countbecause the second emergency mesh might have a lower bandwidth, dataspeed, and/or throughput than that of the first emergency mesh. In someembodiments, the access point 705 h might not switch to the secondemergency mesh if the access point 705 h has been pre-designated to be apart of the first emergency mesh. In some embodiments, the access point705 h might not switch to the second emergency mesh if it is not part ofan emergency service area to which the access point 705 h has beenassigned.

In some embodiments, each of the access points 705 a-k may include ahardware-level network rebuild component. In such embodiments, therebuild component may aid each of the access points 705 a-k to determineits state or mode (e.g., an emergency mesh mode) and whether there isnetwork connectivity over the distribution network (e.g., networkconnectivity over the HFC plant). Further, the rebuild component mayhave additional tuning capabilities in the radio to sense and receivethe strongest adjacent access point broadcast signals.

In one or more embodiments, the mesh server 108 may establish multiplesemergency search areas (ESAs), such as, for example, a first ESA 710 aand a second ESA 710 b. Each ESA 710 a-b may be respectively associatedwith a first emergency mesh and a second emergency mesh. Each ESAa 710a-b may include one or more access points, one or more lines (e.g.,fiber nodes), one or more headend devices (e.g., CMTSs), one or moreswitches, and/or the like. The mesh server 108 may limit the totalnumber of access points in any given ESA so that each access point mayhave a throughput above a predetermined threshold and/or reducebottlenecks below a predetermined throughput. In other words, the meshserver 108 may send an instruction to one or more access points toprevent one or more particular access points from joining a particularemergency mesh. For example, the mesh server 108 may send an instructionto access point 705 g to prevent access point 705 h from joining thesecond wireless mesh because access point 705 h is assigned to the firstESA 710 a and access point 705 g is assigned to the second ESA 710 b. Asa result, when the access point 705 h attempts to join and/or switch tothe second emergency mesh, the access point 705 g may reject the requestto join and/or connect to the access point 705 g to join the secondemergency mesh. In some embodiments, the mesh server 108 may determinehow many and which access points are in a particular ESA based on ananticipated and/or actual amount of data or voice traffic, amount ofconnections (e.g., hops), and the like.

In some embodiments, adjacent ESAs may be joined where the scope ofaffected service is large enough (e.g., beyond a predeterminedthreshold). For example, the first ESA 710 a may be joined with thesecond ESA 710 b to maintain a bandwidth or throughput above apredetermined threshold for access point 705 f.

In one or more embodiments, the access points 705 a-k (e.g., a set-topbox, eDVA, Wi-Fi hotspot, etc.) may receive from the mesh server 108 anemergency mode configuration. The access points 705 a-k may receive theemergency mode configuration via the distribution network and/or anemergency wireless mesh. The access points 705 a-k may receive theemergency mode configuration before, during, and/or after a networkfailure. In some embodiments, when one or more access points 705 a-kdetect a loss of network connectivity over its assigned distributionnetwork (e.g., default HFC lines) for a predetermined time period, theaccess points 705 a-k may switch from a default mode to an emergencymode (i.e., trigger an emergency mode). In some embodiments, theemergency mode may be triggered by the mesh server 108 by sending anemergency mode signal to the egress access points 705 a-b and then theemergency mode signal may be forwarded by the access points 705 a-kuntil each of the access points 705 a-k receives the emergency modesignal. In some embodiments, the emergency mode signal may include theemergency mode configuration. In some embodiments, simultaneously, asession initiated protocol (SIP), network-based calling signaling (NCS),media gateway control protocol (MGCP), and/or simple network managementprotocol (SNMP) message may be broadcast by the mesh server 108 to allreachable access points 705 a-k to switch them into emergency mode.

The emergency mode configuration may include an emergency SSID for useby the access points 705 a-k in bridging their wireless connection withone another to establish one or more emergency meshes. The emergencySSID may be different from a public SSID provided by the serviceprovider and a private SSID of each of the access points 705 a-k. Afterswitching to the emergency mode, the access points 705 a-k may searchfor or detect other access points broadcasting the emergency SSID andconnect to them. In some embodiments, the emergency mode configurationmay include a low power mode. In such embodiments, if an access point(e.g., the access point 705 d) detects that it is no longer receivingpower either through the HFC lines and/or another external power source,then the access point 705 d may preserve power by disabling the accesspoint's 705 d cable modem and line cards to extend the battery life ofthe access point 705 d as long as possible. The access point 705 d maycontinue to use power to maintain a wireless connection with adjacentaccess points 705 a,c,e. The access point 705 d may continue to providea wireless connection even if the access point 705 d (e.g., an eDVA) hasbeen completely dislocated from the residence or business (for example,the access point 705 d is now in the front yard). The access point 705 dmay continue to operate on battery power and may continue to remainconnected to the first emergency mesh. In some embodiments, consumerpremise equipment (e.g., tablet, computers, cell phones, etc.) mayreceive the emergency mode configuration. In such embodiments, once theaccess point 705 d exhausts the power from its battery, these devices atthe same premise or location as access point 705 d may connect toadjacent access points 705 a,c,e using the emergency SSID. In someembodiments, these devices may download a service provider appassociated with the emergency service.

The access points 705 a-k, when in emergency mode, may limit the amountof traffic and/or prioritize the type of traffic going through theaccess points 705 a-k to maintain throughput above a predeterminedthreshold for the emergency meshes. For example, the access point 705 dmay block requests for a first content type (e.g., from the access point705 e) and may permit requests for a second content type different fromthe first content type (e.g., from the access point 705 e). For example,the access point 705 d may block requests associated with games, movies,and/or other media but may permit (e.g., forward) requests for emergencyservices and critical applications.

Further, the access points 705 a-k, when in emergency mode, may limitthe types of devices that the access points 705 a-k will let transmitand/or receive data in order to maintain throughput above apredetermined threshold for the emergency meshes. For example, theaccess point 705 e may be connected to multiple consumer premisedevices. For example, the access point 705 e may have a gaming console,a set-top box, a computer, a tablet, or the like connected to its Wi-Fihotspot at the access point 705 e. Each device may include a mediaaccess control (MAC) address and may be located, along with the accesspoint 705 e, at the user's residence. The access points 705 a-k mayidentify the devices based on their MAC addresses. For example, theaccess points 705 a,d-e may identify a particular gaming device based onan organizationally unique identifier (OUI) (e.g., the first six digits)of its MAC address. At least one of the access points 705 a,d-e mayprevent and/or block requests to a headend device from a first device(e.g., the gaming console) of the user but may permit (e.g., forward)requests to the headend device from a second device (e.g., the set-topbox) of the user.

As the service comes back up (e.g., as access points regain connectivitythrough the distribution HFC network), the mesh server 108 may updatethe one or more of the emergency meshes and the ESAa 710 a-b to permitgreater overall throughput to the access points 705 a-k. For example,the access point 705 i may regain its network connectivity over the HFClines. In response, the mesh server 108 may identify access point 705 ias an egress access point. In some embodiments, the mesh server 108 mayexpand the second ESA 710 b to also include access points 705 e-f,hbecause the second ESA 710 b has an additional egress access point. Themesh server 108 may contract the first ESA 710 a so that it might notinclude access points 705 e-f,h. In some embodiments, the mesh server108 may establish a third ESA associated with access points 705 i-k andmay contract the second ESA 710 b so that it might not include accesspoints 705 i-k. In some embodiments, the mesh server 108 may also updatethe priority of content and devices. For example, the mesh server 108may signal to one or more access points 705 a-k to now permit gamingcontent and requests from gaming consoles. In some embodiments, theaccess points 705 a-k may continue to block certain types of content(e.g., high definition content) and/or particular types of devices thatuse above a predetermined threshold of bandwidth.

In one or more embodiments, the mesh server 108 may send to one or moreof the access points 705 a-k an instruction to propagate broadcastmessages to other access points 705 a-k. As a result, as each of theaccess points 705 a-k becomes a part of one of the emergency meshes,those access points 705 a-k may send messages (e.g., alert messages) toone or more of the other access points 705 a-k. Further, the mesh server108 may send messages to the one or more access points 705 a-k and mayreceive messages from the one or more access points 705 a-k. The messagemay be initiated by one of the access points 705 a-k and/or the meshserver 108. The messages may be transmitted by the access points 705 a-kusing the emergency SSID and/or a respective private SSID of theparticular access point. When the message is received by one of theaccess points 705 a-k, that particular access point may output themessage to one of the consumer premise devices (e.g., a computer,set-top box, etc.) connected with the particular access point so thatthese devices may display the alert message to the user. The particularaccess point may forward (e.g., relay) the alert message to other accesspoints.

The mesh server 108 may identify any access point that might not beconnected to an emergency mesh (using e.g., the generated contour map)and may send that access point the alert message over another network(e.g., a cellular network). Additionally or alternatively, the meshserver 108 may identify an area near that access point at which a mobilevehicle of the service provider may be placed in order to connect thataccess point to the emergency mesh.

Each of the access points 705 a-k may send an emergency communicationpacket to one or more consumer premise devices (e.g., life alert,cellular phones, etc.). The emergency communication packet may include,for example, the emergency SSID, the private SSID of a particular accesspoint, an instruction to use a voice over internet protocol (VoIP), aninstruction to use a GPS location request protocol, and/or aninstruction to use any other protocols. For example, if a cellular towerstops working and a cellular phone places a call to an emergencyresponder (e.g., the fire department), then rather than connecting thecall through the cellular tower the call may be connected via theemergency mesh using VoIP. More specifically, a cellular phone withinwireless communication range of access point 705 e may communicate withthe emergency responder by wirelessly connecting with the access point705 e using the emergency SSID and/or the private SSID of access point705 e. The access point 705 e may then relay the call to a headenddevice (e.g., mesh server 108) using the first emergency mesh. The meshserver 108 may then relay the call to the emergency responder. Theemergency responder may send voice data to the cellular phone by sendingthe voice data to the mesh server 108, which then relays the voice datato the access points 705 a,d,e and then to the cellular phone toestablish communication between the cellular phone and the emergencyresponder. Other messages (e.g., short messaging service (SMS) messages,instant messages, emails, etc.) may be sent and received in a similarmanner.

The GPS location request protocol may include instructions for thedevice (e.g., cellular phone) to transmit its GPS coordinate informationso that the mesh server 108 may relay the GPS information to theemergency responders. In the event the cellular phone might not be ableto transmit its GPS coordinate information, one or more neighboringaccess points (e.g., access point 705 e) may transmit to the mesh server108 an indication that the cellular phone is within their respectivewireless coverage range. The mesh server 108 may triangulate and/orotherwise approximate the location of the cellular phone and may relaythe approximated location of the cellular phone to the emergencyresponders.

In some embodiments, the mesh server 108 may, using a generated coveragemap as discussed herein, identify one or more locations to place a cellbackup tower so that there may be a backup route of communicating to theaccess points 705 a-k.

In some embodiments, the access points 705 a-k may continuously listenfor the emergency SSID. As a result, the mesh server 108 may, using theemergency SSID, send a message to the access points 705 a-k via bridgingwireless connections as discussed above even when the access points 705a-k are in a non-emergency mode. For example, the message may be aninstruction for one or more devices to reboot.

In some embodiments, the mesh server 108 may develop a disastermanagement plan. For example, the mesh server 108 may determine thescope of a disaster by analyzing which access points have lost networkconnectivity through their assigned distribution network (e.g., HFClines). The mesh server 108 may update a generated coverage map to showwhich access points have lost network connectivity over their assigneddistribution network. The mesh server 108 may transmit the generatedcoverage map showing network outages to emergency responders.

FIG. 9 illustrates an exemplary system for modeling a wireless networkin accordance with one or more illustrative aspects discussed herein.The system 900 may include multiple access points 905 (e.g., eDVAs,EMTAs, modems, or the like) connected to at least one of the headends910 a-b through fiber optic connections 915 and fiber nodes 920. Thefiber nodes 920 may be respectively associated with fiber node servingareas 925. In an exemplary embodiment, the system 900 may include sixfiber nodes 920, six fiber optic connections 915, and six fiber nodeserving areas 925.

FIG. 10 illustrates a flowchart of an exemplary method for modeling awireless network in accordance with one or more illustrative aspectsdiscussed herein. In one or more embodiments, the method of FIG. 10and/or one or more steps thereof may be performed by a computing device(e.g., computing device 200). In other embodiments, the methodillustrated in FIG. 10 and/or one or more steps thereof may be embodiedin computer-executable instructions that are stored in acomputer-readable medium, such as a non-transitory computer-readablememory.

As seen in FIG. 10, the method may begin at step 1005 in which headends910 a-b may determine multiple sets of fibers nodes. For example, instep 1005, the first headend 910 a may determine that the first headend910 a is connected with three of the six fiber nodes 920 (e.g., a firstfiber node, a second fiber node and a third fiber node). The firstheadend 910 a may determine each of the fiber node serving areas 925associated with each the first three fiber nodes 920. The first headend910 a may determine each of the access point 905 on each of the firstthree fiber nodes 920.

Similarly, the second headend 910 b may determine that the secondheadend 910 b is connected with three of the six fiber nodes 920 (e.g.,a fourth fiber node, a fifth fiber node and a sixth fiber node). Thesecond headend 910 b may determine each of the fiber node serving areas925 associated with each the last three fiber nodes 920. The secondheadend 910 b may determine each of the access point 905 on each of thelast three fiber nodes 920.

In some embodiments, the headends 910 a-b may determine the aboveinformation by, for example, retrieving the information from one or moredatabases of the headends 910 a-b and/or by analyzing a generatedcoverage map as discussed herein.

In step 1010, the headends 910 a-b may generate an index of adjacentfiber nodes. For example, in step 1010, one or both headends 910 a-b maydetermine that the first of the six fiber nodes 920 may be adjacent tothe second, third, and fifth of the six fiber nodes 920. The headends910 a-b may determine that the second of the six fiber nodes may beadjacent to first, third, and fourth of the six fiber nodes 920. Theheadends 910 a-b may determine that the third of the six fiber nodes 920may be adjacent to the first, second, fourth, and fifth of the six fibernodes 920. The headends 910 a-b may determine that the fourth of the sixfiber nodes 920 may be adjacent to second, third, fifth, and sixth ofthe six fiber nodes 920. The headends 910 a-b may determine that thefifth of the six fiber nodes 920 may be adjacent to the first, third,fourth, and sixth of the fiber nodes 920. The headends 910 a-b maydetermine that the sixth of the six fiber nodes may be adjacent to thefourth and fifth of the six fiber nodes 920. In some embodiments, theheadends 910 a-b may determine the adjacencies by analyzing thegenerated coverage map discussed herein.

In step 1015, the headends 910 a-b may model each of the egress accesspoints to determine which egress access points would create the optimumconnections and throughput for an emergency mesh. For example, in step1015, the headends 910 a-b may determine one or more planned egressaccess points by analyzing each egress access point (e.g., one or moreof the access points 905 with network connectivity over one of the fiberoptic connections 915). For example, the first headend 910 a may analyzethe connection quality (e.g., data speed, bandwidth, signal strength,etc.) between the first headend 910 and each of the egress accesspoints. For example, the first headend 910 a may select a particularegress access point to become a “root” node for an emergency mesh whenthe particular egress access point has one or more of a higher dataspeed, greater bandwidth, and/or greater signal strength than that ofanother egress access point.

For example, the first headend 910 a may analyze the geographicalproximity of each of the egress access points to a boundary of theirassociated fiber node serving area 925. In other words, the firstheadend 910 a may determine a distance between an egress access pointand the boundary of its fiber node service area 925. For example, thefirst headend 910 a may select a particular egress access point tobecome a “root” node for an emergency mesh, for example, when a distancebetween the particular egress access point and the boundary is above apredetermined threshold and/or greater than a distance of another egressaccess point.

For example, the first headend 910 a may analyze a number of expecteddownstream connections over the fiber optic connections 915. Forexample, the first headend 910 a may determine the number of currentegress access points and/or the number of egress access points that maybe a “root” node for an emergency mesh. The first headend 910 a may alsopredict a number of access points (that might not currently have networkconnectivity over the fiber optic connections 915) but that may beexpected to become egress access points (e.g., regain networkconnectivity) within a predetermined period of time.

Similarly, the second headend 910 b may perform similar determinationsfor its egress access points. For example, the second headend 910 b mayanalyze connection quality between the second headend 910 b and each ofthe egress access points. For example the second headend 910 b mayanalyze the geographical proximity of each of its egress access pointsto a boundary of their associated fiber node serving area 925. Forexample, the second headend 910 b may analyze the number of expecteddownstream connection over the fiber optic connections 915.

In step 1020, the headends 910 a-b may generate a node mesh model. Forexample, in step 1020, the headends 910 a-b may determine how manyaccess points and/or hops (as discussed above in FIG. 7) a particularemergency mesh may include while maintaining a data speed, bandwidthcapacity, and/or throughput above a predetermined threshold value basedon the determination and analysis performed in step 1015. For example, apotential emergency mesh may include at least a portion of one or morefiber node serving areas 925. A potential mesh may be commensurate withone or more fiber node serving areas 925. For example, a potential meshmay include access points 905 associated with two or more adjacent fibernodes 920 determined in steps 1005 and 1010.

In step 1025, the headends 910 a-b may generate a super-node model. Forexample, in step 1025, the headends 910 a-b may create one or moreemergency meshes that span more than two fiber serving areas 925. Forexample, in the event that the second headend 910 b is no longerfunctioning, an emergency mesh may be used to connect the access points905 of each of the six fiber node serving areas 925. The emergency meshmay have one or more “root” nodes (e.g., egress access points) withnetwork connectivity over the fiber optic connections 915 to the firstheadend 910 a.

In some embodiments, each of the steps 1005-1025 may be performed by themesh server 108. While only six fiber nodes 920 and two headends 910 a-bwere discussed, in some instances, there may be fewer or additionalfiber nodes and/or headends.

Referring back to FIG. 9, the headends 910 a-b may include multipleCMTSs (not shown) and associated backplane routers (not shown) to routedata to the access points 905. Each CMTS may include a dedicated routerbackplane and have an initial (e.g., default) transiting traffic routein its network core. In the event an emergency mesh is established inwhich one or more egress access points may relay data to one or moreaccess points 905, the headends 910 a-b (and/or mesh server 108) maydedicate more router backplane to a CMTS connected to an egress accesspoint. The headends 910 a-b (and/or mesh server 108) may update data andvoice balances on one or more of the CMTSs to accommodate communicationson the emergency mesh. The headends 910 a-b (and/or mesh server 108) mayreroute transiting traffic in network core to provider service to accesspoints 905 that have lost network connectivity over the distributionnetwork. For example, a CMTS that transmitted data to a first routerduring the initial route of transiting data may now transmit data to asecond different router during the new route of transiting data.Additionally, the headends 910 a-b may port filter downstream traffic toeliminate non-critical traffic.

In some embodiments, the service provider may coordinate with otherservice providers to permit emergency meshes to include access points ofthe service provider to connect with access points and/or headends ofthe other service provider. In some embodiments, the bridging thewireless connections of access points may span large distances (e.g.,cities).

While the above embodiments may refer to Wi-Fi wireless connections,other wireless connections may be used in any of the above embodimentsincluding, for example, satellite connections, cellular connections,Bluetooth connections, or any other wireless connection. In someembodiments, multiple different types of wireless connections may beused within an emergency mesh.

Although the subject matter disclosed herein has been described inlanguage specific to structural features and/or methodological acts, itis to be understood that the subject matter defined in the appendedclaims is not necessarily limited to the specific features or actsdescribed above. Rather, the specific features and acts described aboveare disclosed as example forms of implementing the claims.

What is claimed is:
 1. A method comprising: receiving, by a firstwireless access device, from a second wireless access device, and via apublic network indicated by a public service set identifier (SSID), afirst message comprising a private SSID associated with the secondwireless access device; in response to a determination that the firstwireless access device does not have network connectivity with a headenddevice, sending, by the first wireless access device, to a thirdwireless access device, and via the public network indicated by thepublic SSID, a second message comprising a private SSID associated withthe first wireless access device, wherein the third wireless accessdevice is different from the second wireless access device; andestablishing a wireless network between the first wireless access deviceand the second wireless access device using the private SSID associatedwith the second wireless access device and between the first wirelessaccess device and the third wireless access device using the privateSSID associated with the first wireless access device.
 2. The method ofclaim 1, further comprising: communicatively connecting the firstwireless access device with the headend device through a first set ofone or more intermediate wireless access devices, wherein the first setof one or more intermediate wireless access devices comprises at leastthe second wireless access device, and wherein the first messagecomprises a first hop count of the first set of one or more intermediatewireless access devices between the first wireless access device and theheadend device; receiving, by the first wireless access device, a thirdmessage comprising a second hop count of a second set of one or moreintermediate wireless access devices between the first wireless accessdevice and the headend device; and in response to a determination thatthe second hop count is less than the first hop count, disconnecting thefirst wireless access device from the first set of one or moreintermediate wireless access devices and connecting the first wirelessaccess device to the second set of one or more intermediate wirelessaccess devices.
 3. The method of claim 1, further comprising: inresponse to determining that the first wireless access device hasregained network connectivity with the headend device, sending a requestfor an increase in provisioned bandwidth to the headend device.
 4. Themethod of claim 1, further comprising: receiving, by the first wirelessaccess device and in the first message, a first hop count of a first setof one or more intermediate devices between the first wireless accessdevice and the headend device; and incrementing the first hop count to asecond hop count, wherein the second message comprises the second hopcount.
 5. The method of claim 1, further comprising, prior to thereceiving, determining that the second wireless access device hasestablished a connection via one or more other wireless access devicesto the headend device.
 6. The method of claim 1, further comprising:receiving, by the first wireless access device, an ordered list ofwireless access devices with which to attempt to establish a connectionif a loss of connectivity between the first wireless access device andthe headend device is detected for at least a predetermined time period.7. The method of claim 1, further comprising: prior to the receiving,transmitting, by the first wireless access device and to the secondwireless access device, a first request inquiring whether the secondwireless access device has network connectivity to the headend device;receiving, by the first wireless access device and from the secondwireless access device, an indication that the second wireless accessdevice does not have network connectivity to the headend device; andafter waiting a period of time, transmitting, by the first wirelessaccess device and to the second wireless access device, a second requestinquiring whether the second wireless access device has networkconnectivity to the headend device.
 8. The method of claim 1, furthercomprising: establishing a communicative connection between the firstwireless access device and a first cable modem termination system (CMTS)via the second wireless access device, wherein the second wirelessaccess device is assigned to the first CMTS, and wherein the firstwireless access device is assigned to a second CMTS different from thefirst CMTS.
 9. A method comprising: receiving, by a first wirelessaccess device, from a second wireless access device, and via a publicnetwork indicated by a public service set identifier (SSID), a firstmessage comprising a private SSID associated with the second wirelessaccess device and a first hop count of a first set of one or moreintermediate wireless access devices between the first wireless accessdevice and an upstream network device; establishing a wirelessconnection between the first wireless access device and the secondwireless access device using the private SSID associated with the secondwireless access device; receiving, by the first wireless access device,from a third wireless access device, and via the public networkindicated by the public SSID, a second message comprising a private SSIDassociated with the third wireless access device and a second hop countof a second set of one or more intermediate wireless access devicesbetween the first wireless access device and the upstream networkdevice; and comparing, by the first wireless access device, the firsthop count with the second hop count.
 10. The method of claim 9, furthercomprising: in response to determining that the first hop count is lessthan the second hop count, maintaining, by the first wireless accessdevice, the wireless connection with the second wireless access device.11. The method of claim 9, further comprising: in response todetermining that the second hop count is less than the first hop count,disconnecting the first wireless access device from the second wirelessaccess device and establishing a wireless connection between the firstwireless access device and the third wireless access device using theprivate SSID associated with the third wireless access device.
 12. Themethod of claim 9, further comprising: incrementing, by the firstwireless access device, the first hop count by one; and transmitting, bythe first wireless access device, to a fourth wireless access device,and via the public network indicated by the public SSID, a third messagecomprising the incremented first hop count.
 13. The method of claim 9,further comprising: prior to the receiving the first message,transmitting, by the first wireless access device and to the secondwireless access device, a first request inquiring whether the secondwireless access device has network connectivity to the upstream networkdevice; receiving, by the first wireless access device and from thesecond wireless access device, an indication that the second wirelessaccess device does not have network connectivity to the upstream networkdevice; and after waiting a period of time, transmitting, by the firstwireless access device and to the second wireless access device, asecond request inquiring whether the second wireless access device hasnetwork connectivity to the upstream network device.
 14. The method ofclaim 9, further comprising: determining that the first wireless accessdevice has regained network connectivity with the upstream networkdevice; and receiving, by the first wireless access device, an increasein provisioned bandwidth.
 15. The method of claim 9, further comprising:establishing a communicative connection between the first wirelessaccess device and a first cable modem termination system (CMTS) via thesecond wireless access device, wherein the second wireless access deviceis assigned to the first CMTS, and wherein the first wireless accessdevice is assigned to a second CMTS different from the first CMTS.
 16. Asystem comprising: a first wireless access device; a second wirelessaccess device; a third wireless access device; and a headend device,wherein the first wireless access device comprises one or morecomputer-readable media storing one or more computer-executableinstructions that, when executed by the first wireless access device,cause the first wireless access device to: receive, from the secondwireless access device and via a public network indicated by a publicservice set identifier (SSID), a first message comprising a private SSIDassociated with the second wireless access device; in response to adetermination that the first wireless access device does not havenetwork connectivity with the headend device, send, to the thirdwireless access device and via the public network indicated by thepublic SSID, a second message comprising a private SSID associated withthe first wireless access device; and establish a wireless networkbetween the first wireless access device and the second wireless accessdevice using the private SSID associated with the second wireless accessdevice and between the first wireless access device and the thirdwireless access device using the private SSID associated with the firstwireless access device.
 17. The system of claim 16, wherein the one ormore computer-readable media storing the one or more computer-executableinstructions, when executed by the first wireless access device, furthercause the first wireless access device to: communicatively connect thefirst wireless access device with the headend device through a first setof one or more intermediate wireless access devices, wherein the firstset of one or more intermediate wireless access devices comprises atleast the second wireless access device, and wherein the first messagecomprises a first hop count of the first set of one or more intermediatewireless access devices between the first wireless access device and theheadend device; receive, a third message comprising a second hop countof a second set of one or more intermediate wireless access devicesbetween the first wireless access device and the headend device; and inresponse to a determination that the second hop count is less than thefirst hop count, disconnect the first wireless access device from thefirst set of one or more intermediate wireless access devices andconnect the first wireless access device to the second set of one ormore intermediate wireless access devices.
 18. The system of claim 16,wherein the one or more computer-readable media storing the one or morecomputer-executable instructions, when executed by the first wirelessaccess device, further cause the first wireless access device to: inresponse to determining that the first wireless access device hasregained network connectivity with the headend device, send a requestfor an increase in provisioned bandwidth to the headend device.
 19. Thesystem of claim 16, wherein the one or more computer-readable mediastoring the one or more computer-executable instructions, when executedby the first wireless access device, further cause the first wirelessaccess device to: receive, in the first message, a first hop count of afirst set of one or more intermediate devices between the first wirelessaccess device and the headend device; and increment the first hop countto a second hop count, wherein the second message comprises the secondhop count.
 20. The system of claim 16, wherein the one or morecomputer-readable media storing the one or more computer-executableinstructions, when executed by the first wireless access device, furthercause the first wireless access device to: receive an ordered list ofwireless access devices with which to attempt to establish a connectionif a loss of connectivity between the first wireless access device andthe headend device is detected for at least a predetermined time period.